Excellent, thanks for the quick response!

You're right. This was a bug caused by bouncing off the inside of a piece of airspace (laterally) hitting a vertex exactly, and coming back on yourself. A mathematical edge case in our hit testing. We have fixed it ready for the next version. Thanks for bringing it to our attention!

Very odd - I see the same behaviour on both Win10 and Android versions. Curiously if you approach THRED from the south, everything works correctly. I suspect it's some strange effect caused by having a waypoint exactly on a zone boundary with the flight path touching but not actually crossing the boundary, however I can't trigger the same bug with ORTAC, MID, RIDL or TRIPO. Most curious!

I was messing around the other day and seem to have discovered a problem with airspace display. I planned this:



All seems fine. However, if I move the second waypoint from 'random place north of THRED' to THRED itself, I get this:

According to the Virtual Radar display, I no longer enter the Solent CTA, as it seems to have moved! The airspace warning from the 'Flight Details' tab is also gone.